Skip to content

Update CHANGELOG.md for 5.5.1 #891

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

Andrew-Chen-Wang
Copy link
Member

@Andrew-Chen-Wang Andrew-Chen-Wang commented Mar 14, 2025

re the issue here #884 (comment), we also had lots of great contributions that we can release

@Andrew-Chen-Wang Andrew-Chen-Wang requested a review from a team March 14, 2025 02:06
@Andrew-Chen-Wang
Copy link
Member Author

I wrote $$. will fix later don't merge

@mjbogusz
Copy link

Is there a chance that #861 will be included as well?

@lordoffreaks
Copy link

Hi!

Thanks a lot for the work and catching and fixing #884 so quickly ... do you have any estimate for the release of 5.5.1?

@vgrozdanic
Copy link
Contributor

Is there a chance that #861 will be included as well?

@mjbogusz no, since it would require major release rather than just a patch release - #861 introduces a breaking change.

There is an open issue which tracks what needs to be done before a major release: #871 (it has #861 included in there)

@vgrozdanic
Copy link
Contributor

vgrozdanic commented Mar 23, 2025

@Andrew-Chen-Wang can we also include #894 in a release - it adds no-op migrations that are needed because Meta attribute of the models were updated?

@vgrozdanic
Copy link
Contributor

@Andrew-Chen-Wang any chance we can do a release?

I have seen that there is a duplicate issue opened, and it has been recently fixed: #900, so to prevent similar issue opening, maybe we can do a release soon :)

@robertalexa
Copy link

hey guys, any update on this release?

@robertalexa
Copy link

@vgrozdanic With the risk of spamming, any updates on this?

@@ -1,3 +1,14 @@
$$ 5.5.1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is one more fix:

Suggested change
$$ 5.5.1
$$ 5.5.1
* fix: add missing migration for token_blacklist app by @juanbailon in https://github.com/jazzband/djangorestframework-simplejwt/pull/894

Just not sure if we want to put this disclaimer to the changelog: #894 (comment)

@vgrozdanic
Copy link
Contributor

@vgrozdanic With the risk of spamming, any updates on this?

@robertalexa sorry i have missed previous comment.

Only @Andrew-Chen-Wang from active maintainers has permissions to do releases. I have just merged one last change for 5.5.1, so when Andrew will have time i think we are good to release :)

@hakan-77
Copy link

Hi all, any updates on 5.5.1 release? Particularly for #831
We have been holding pyjwt upgrade for a while..

@Andrew-Chen-Wang
Copy link
Member Author

Andrew-Chen-Wang commented May 31, 2025

Hi folks, super sorry for the delay. @vgrozdanic what additional PRs need to be merged? if none, let me know if we should just make a release based on this PR! Feel free to directly edit this branch as well. I'll block out some time next weekend to look to release.

@vgrozdanic
Copy link
Contributor

Hi all, any updates on 5.5.1 release? Particularly for #831 We have been holding pyjwt upgrade for a while..

@hakan-77 regarding the #831 we will release the fix for it in the next major version (6.0.0) which will go after 5.5.1 is released. Most of the work has already been done to address this, but will only be merged after we release 5.5.1

@vgrozdanic
Copy link
Contributor

Hi folks, super sorry for the delay. @vgrozdanic what additional PRs need to be merged? if none, let me know if we should just make a release based on this PR! Feel free to directly edit this branch as well. I'll block out some time next weekend to look to release.

@Andrew-Chen-Wang awesome! Everything is already merged, i have updated the changelog with 2 more PRs that were merged after you opened this PR.

There's one more thing i am not sure about, and that is how to include the disclaimer for users who by accident generated a migration for this app (we can maybe c/p it from this comment: #894 (comment)). So far there has been no such case in the changelog, and not sure how you would want to include it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants